System and method for a serialized data service

ABSTRACT

The present disclosure includes a system and method for a serialized data service. A method for a serialized data service includes retrieving serialized data to a data service, and augmenting the serialized data with information corresponding to one or more data retention policies. The augmented serialized data is stored to a data source. The augmented serialized data is removed from the data source based on the augmented information.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is related to (1) PCT Application serial number PCT/US2010/040577, entitled “System and Method for Service Recommendation Service,” filed on the same date as the present application, (2) PCT Application serial number PCT/US2010/040608, entitled “System and Method for Collaborative Information Services,” filed on the same date as the present application, (3) PCT Application serial number PCT/US2010/040592, entitled “System and Method for Automated Data Discovery Service,” filed on the same date as the present application, and (4) PCT Application serial number PCT/US2010/040597, entitled “System and Method for Self-Service Configuration of Authorization,” filed on the same date as the present application, the disclosures which are incorporated herein by reference.

BACKGROUND

Information can have great value. Assembling and maintaining a database to store information involves real costs. The costs can include the costs to acquire the information, the costs associated with the physical assets used to house, secure, and make the information available, and/or the labor costs to manage the information.

Some of the value of certain information may be derived from the fact that the information is not widely known (e.g., not shared). For example, a list of suppliers, their products and pricing, or a customer list, may be valuable to a manufacturing entity, which likely would not be inclined to share such information with its competitors. Conversely, some of the value of other information may be derived from the fact that the information is widely known (e.g., shared). For example, a library catalog is information that can be valuable to a community of users by being widely available, thereby saving time, effort, and perhaps money in trying to locate a particular item in a collection of items.

Some competitive information that principally derives value from not being widely known (e.g., among competitors and/or customers) may derive additional value were it shared with other entities in a limited manner. One such example is information related to a supply chain. A supply chain is a system of organizations, people, technology, activities, information and resources involved in moving a product or service from supplier to customer. A service can include a wholly electronic workflow, in which case “fulfillment” is the completion of a specific set of possibly entirely-electronic tasks, with the appropriate temporal ordering. A supply chain may be a combination of products and services. For example, services that monitor and provide local control over electricity usage by customers may help to control the generation and supply of electricity to customers. Relationships of participants in a supply chain may include supplier-customer, and/or competitors, among others. Regulators and/or consumers may also have an interest in information concerning a particular supply chain. For example, information regarding the supply chain of a food product may be of interest to regulators and/or consumers.

It may be beneficial to share information on a limited basis to demonstrate that a certain component is not involved, or otherwise trace items and/or processes involved in the supply chain. It may be desirable to share information on a limited basis for studies that might benefit multiple supply chain entities and/or the consumers, or to prove or disprove some fact to regulators. Increased traceability can also limit the potentially huge economic and safety consequences of counterfeiting and defective products. For example, food and/or brand name piracy concerns can cost the industry billions of dollars each year, and can cause the industry to implement anti-counterfeit technologies to protect products, brand and/or market. Recall is also a critical service where remedial activities are to be applied to a defective product or component thereof, making it desirable to identify locations of affected product. Increased traceability along a supply chain can increase trust and limit the consequences of events closer to their source in the supply chain.

Enhanced supply chain robustness improves customer experience by delivering products reliably and decreasing the costs and manual effort associated with debugging and fixing errors in the delivery of products and services. Supply chain participants are motivated to improve robustness but need improved mechanisms to efficiently manage the sharing of information. Collaborative information systems can include large amounts of dynamic data, such as concerning transactional information of products and/or services of a supply chain. Applying appropriate data retention policies to data sources that may be geographically and organizationally diverse, subject to multiple legal requirements, and can be maintained over long periods of time as data-related considerations change, can be challenging.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a computing system according to an example of the present disclosure.

FIG. 2A is a diagram illustrating an example computing platform for providing collaborative information services according to an example of the present disclosure.

FIG. 2B is a diagram illustrating another example computing platform for providing collaborative information services according to an example of the present disclosure.

FIG. 3 is a diagram illustrating components of the collaborative information services platform according to an example of the present disclosure.

FIG. 4 is a diagram illustrating an authorization and attestation service for a computing platform according to an example of the present disclosure.

FIG. 5 is a diagram illustrating a discovery service for a computing platform according to an example of the present disclosure.

FIG. 6 is a diagram illustrating a cloud index cache arrangement according to an example of the present disclosure.

FIG. 7 is a diagram illustrating a serialized data service according to an example of the present disclosure.

FIG. 8 is a flow chart illustrating an example of a method for serialized data service according to an example of the present disclosure.

DETAILED DESCRIPTION

The present disclosure includes a system and method for a serialized data service. An example method for a serialized data service [801] includes retrieving serialized data to a data service [803], and augmenting the serialized data with information corresponding to one or more data retention policies [809]. The augmented serialized data is stored to a data source [811]. The augmented serialized data is removed from the data source based on the augmented information [813].

The collaborative information system of the present disclosure is arranged generally in a hub-and-spokes configuration, with a collaborative information services (CIS) computing platform programmed with query services as a hub, and participant data sources as the spokes. Participants in the collaborative information system make some portion of their respective data sources available to queries of other participants. According to the present disclosure, participants authorize query services with constrained data inputs and known output attributes. A query service is a group of one or more queries executed to ascertain information of interest. A query set is a number of queries that can be related to one another in some aspect. A query service may include queries from one or more query sets, or the queries comprising multiple query services may all be included in a single query set. That is, a query service may be a subset of one or more query sets, or multiple query services may be subsets of a single query set, depending on the queries comprising the query set(s) and the query service(s).

According to the collaborative information system of the present disclosure, attributes of each query service are defined prior to the query service being invoked by any participant. Each data source controlling entity must implement pre-defined queries of a query service to involve their respective data source. For example, the type of data and scope of data sources associated with a particular query service is pre-defined, the attributes of a respective query service being made available to participants so that they can determine whether, and to what extent, to expose their respective data source to the queries of a query service. That is, each query service is implemented using a “canned” group of queries that can be applied to a data source, if authorized by the control entity of the data source and the queries implemented on the respective data source. Similarly, scope, format, etc., of query results are also defined prior to a query service being invoked. Such a pre-defined result may be computed and mutually advantageous for the query invoker and data providers to share. It may obfuscate aspects of the data obtained by the embedded queries to compute intermediate results but that the data providers may not want or need to share directly. This may encourage providers to share more data with the knowledge that those invoking query services only have access to the possibly more limited computed results. Having pre-defined queries in terms of inputs and outputs enables collaborative information system participants to make informed decisions as to the type and extent of queries, and therefore query services, to which they are willing to allow their respective data source to be exposed.

According to the collaborative information system of the present disclosure, information needed for authorized results (e.g., raw data source data, intermediate computations, etc.) may or may not be presented to the participant that invokes a particular query service. In some previous approaches, the data being made available by each participant needed to be stored (e.g., duplicated to) a particular dedicated computing system storage media. However, the collaborative information system of the present disclosure does not require participant-contributed information to be maintained in a common, dedicated location. That is, the collaborative information system of the present disclosure enables participants to self-configure various authorization models that in turn control access of other participants to their data source(s). In this manner, dispersed data sources, including cloud based data sources, can be controlled to the degree desired by the data source control entity at their original location.

According to the collaborative information system of the present disclosure, authorization to access data of a data source is made with respect to query services of the collaborative information services computing platform, rather than peer-to-peer with each participant in the collaborative information system. Thus, the collaborative information system of the present disclosure enables self-configuration of authorizations by participants with fewer interventions by their IT staff. Also, automated and repeated discovery of information available from portions of the data sources available to the query services supports the efficient implementation of real time query services on a large scale.

FIG. 1 is a diagram illustrating a computing system according to an example of the present disclosure. The computing system shown in FIG. 1 is a networked computing system, such as a cloud computing system 100. Cloud computing system 100 is one example implementation of a networked computing system. However, examples of the present disclosure are not limited to a particular computing system configuration. By “cloud computing” is meant Internet-based computing that can effectively share physical computing resources, including software and/or information among a number of users. Cloud computing enables fine-grained provisioning of computing resources in real time to achieve dynamic scalability in response to varying data processing levels.

Cloud computing system 100 can include a private cloud 110 communicatively coupled to a public cloud 102. The public cloud 102 can include a number of computing resources networked together by various communication channels 106, including first computing resources 104 external to a hybrid cloud 112 (discussed further below), and second computing resources external to the hybrid cloud 112. The computing resources 104 comprising the public cloud 102 can be of varying size and capability, may be respectively geographically dispersed from one another or be commonly located, and may be respectively owned and/or operated by any number of independent entities. The size, capabilities, and configuration of public cloud 102 can be dynamically changed as dictated by service level agreements, actual computing requirements, and for other factors applicable to cloud computing arrangements.

The term “public” refers to computing resources offered and/or available for use by entities (e.g., the public) other than the computing resource owners, usually in exchange for compensation (e.g., computing capability for hire). Computing resources 104 comprising the public cloud 102 may be owned by discrete entities, which may or may not be participants in a particular collaborative information system for which the computing resources are being employed.

A respective private owner/operator can make owner/operator-maintained computing resources available to the public for hire. The term “private” refers to computing resources dedicated for use by a limited group of users (e.g., one entity such as a company or other organization). That is, “private” is intended to mean reserved for use by some and not available to the public.

The private cloud 110 can be comprised of a number of computing resources 105. While a single server is shown in FIG. 1, the private cloud can be comprised of multiple computing resources 105. A computing resource 105 can include control circuitry such as a processor, a state machine, application specific integrated circuit (ASIC), controller, and/or similar machine. As used herein, the indefinite articles “a” and/or “an” can indicate one or more than one of the named object. Thus, for example, “a processor” can include one processor or more than one processor, such as a parallel processing arrangement. The control circuitry can have a structure that provides a given functionality, and/or execute computer-readable instructions that are stored on a non-transitory computer-readable medium 107. The non-transitory computer-readable medium 107 can be integral, or communicatively coupled, to a computing resource 105, in either in a wired or wireless manner. For example, the non-transitory computer-readable medium 107 can be an internal memory, a portable memory, a portable disk, or a memory located internal to another computing resource (e.g., enabling the computer-readable instructions to be downloaded over the Internet). The non-transitory computer-readable medium can have computer-readable instructions stored thereon that are executed by the control circuitry (e.g., processor) to provide a particular functionality.

The non-transitory computer-readable medium 107, as used herein, can include volatile and/or non-volatile memory. Volatile memory can include memory that depends upon power to store information, such as various types of dynamic random access memory (DRAM), among others. Non-volatile memory can include memory that does not depend upon power to store information. Examples of non-volatile memory can include solid state media such as flash memory, EEPROM, phase change random access memory (PCRAM), among others. The non-transitory computer-readable medium 107 can include optical discs, digital video discs (DVD), high definition digital versatile discs (HD DVD), compact discs (CD), laser discs, and magnetic media such as tape drives, floppy discs, and hard drives, solid state media such as flash memory, EEPROM, phase change random access memory (PCRAM), as well as other types of machine-readable media.

A data source 115 owned by entity 114 (e.g., organization, natural person) can be part of private cloud 110, or as shown in FIG. 1, communicatively coupled to private cloud 110. That is, information under the control of organization 114 may be stored in the computing resources comprising private cloud 110, or be stored in memory accessible by private cloud 110. The data source 115 may be used in a collaborative information system, with organization 114 making some portion of the information stored in data source 115 available to other participants in the collaborative information system, as is further described below.

Although not shown in FIG. 1 for clarity, private cloud 110 can also include a number of computing resources (e.g., physical resources, software, etc.), such as computing resources 104, networked together by various communication channels 106. The computing resources of private cloud 110 can be homogeneous or of varying size and capability, may be geographically dispersed from one another or be commonly located, and may be owned and/or operated by one or any number of independent entities that dedicate some or all of their computing resources for the private use of one entity (e.g., organization 114). The size, capabilities, and configuration of the private cloud can change as dictated by service level agreements, dynamic computing requirements, and other factors applicable to cloud computing arrangements.

A portion 118 of cloud computing system 100 may be owned by organization 114, and another portion 120 of cloud computing system 100 may be owned by entities other than organization 114. As such, in addition to being private, private cloud 110 may be referred to as an internal cloud as well (e.g., a cloud computing arrangement internal to organization 114 and dedicated to the private use of organization 114). Considerations regarding specific cloud computing system configuration may include security, logging, auditing/compliance, firewall boundary location, and/or company policy, among others. Organization 114 may maintain additional computing resources not dedicated to the private use of organization 114 (e.g., available for contract use by the public as part of a cloud).

A number of entities 116 may be users of the public cloud 102 (e.g., as a networked computing system). Some entities 116 may have data sources 115 that may be used in (e.g., made available for query by participants) a collaborative information system, and other entities 116 using the public cloud may participate in the collaborative information system (e.g., invoke queries) but not have, or make available, a data source to other participants. There are many products from a variety of different vendors that can implement data sources that may be used for collaborative information services via standard interfaces for data queries.

While cloud computing system 100 is illustrated in FIG. 1 as two communicatively coupled clouds (e.g., private and public), examples of the present disclosure are not so limited, and the method of the present disclosure can be implemented using a private cloud 110, public cloud 102, or a hybrid cloud 112 comprising some portion of the public cloud 102 and the private cloud 110 made available for such use.

Not all of the components and/or communication channels illustrated in the figures are required to practice the system and method of the present disclosure, and variations in the arrangement, type, and quantities of the components may be made without departing from the spirit or scope of the system and method of the present disclosure. Network components can include personal computers, laptop computers, mobile devices, cellular telephones, personal digital assistants, or the like. Communication channels may be wired or wireless. Computing devices comprising the computing system are capable of connecting to another computing device to send and receive information, including web requests for information from a server. A server may include a server application that is configured to manage various actions, for example, a web-server application that is configured to enable an end-user to interact with the server via the network computing system. A server can include one or more processors, and non-transitory computer-readable media (e.g., memory) storing instructions executable by the one or more processors. That is, the executable instructions can be stored in a fixed tangible medium communicatively coupled to the one or more processors. Memory can include RAM, ROM, and/or mass storage devices, such as a hard disk drive, tape drive, optical drive, solid state drive, and/or floppy disk drive.

The non-transitory computer-readable media can be programmed with instructions such as an operating system for controlling the operation of server, and/or applications such as a web page server. The collaborative information services (CIS) platform and/or applications (e.g., services and/or models) may be implemented as one or more executable instructions stored at one or more locations within volatile and/or non-volatile memory. Computing devices comprising the computing system implementing the collaborative information system may also include an internal or external database, or other archive medium for storing, retrieving, organizing, and otherwise managing data sources and/or the functional logic of the collaborative information system.

Computing devices comprising the computing system may also be mobile devices configured as client devices, and include a processor in communication with a non-transitory memory, a power supply, one or more network interfaces, an audio interface, a video interface, a display, a keyboard and/or keypad, and a receiver. Mobile devices may optionally communicate with a base station (not shown), or directly with another network component device. Network interfaces include circuitry for coupling the mobile device to one or more networks, and is constructed for use with one or more communication protocols and technologies. Applications on client devices may include computer executable instructions stored in a non-transient medium which, when executed by a processor, provide such functions as a web browser to enable interaction with other computing devices such as a server, and/or the like.

FIG. 2A is a diagram illustrating an example computing platform for providing collaborative information services according to an example of the present disclosure. The systems and methods of the present disclosure for collaborative information services are illustrated throughout this description with respect to a supply chain application of the collaborative information system. However, implementation of the collaborative information system of the present disclosure is not limited to supply chains, and other collaborative information service implementations are contemplated, including SaaS implementations.

A networked computing system implementing collaborative information services (CISs) can be applied to the information associated with a supply chain to provide a secure and trusted registry for supplier and customer information. Such a collaborative information system can act as a cache for information that connects services, partners, and customers. For example, suppliers may register products they sell with the collaborative information system, and customers may register products they use.

The collaborative information system can be used, for example, to provide a recall service upon a product associated with the supply chain. Information in the collaborative information system can cause recall messages to be sent to specific recipients (e.g., existing customers), rather than be broadcast generally (e.g., sent to potential customers as well). Recall messages can include detailed instructions appropriate for a particular recall, or series of recalls. Such a recall service could record the messages sent so that a supplier has the assurance that registered customers are notified.

A customer may also act as a supplier of a product that includes other products as parts. If one of the parts is recalled, then the customer may issue an additional recall via the collaborative information system for the composite product. In this way recall messages can traverse an appropriate portion of the supply chain without being over-, or under-, inclusive.

FIG. 2A illustrates an example architecture of a collaborative information system 222. For example, some, or all, of the participants in the supply chain of interest can be participants 238 in the collaborative information system 222. Collaborative information system participants 238 may have zero or more data sources 240 (e.g., databases, memory) that may be made available to the collaborative information system 222, and other participants 238 therein. Such data sources 240 can be widely deployed, owned and/or controlled by independent entities, and can be implemented with standard interfaces for sharing supply chain information. Some participants 238 of the collaborative information system 222 may not provide a data source to the collaborative information system 222 (e.g., have zero data sources). Some participants 238 of the collaborative information system 222 may participate by invoking query services without offering a data source. For example, regulators or consumers may be collaborative information system participants 238 without also being data source providers.

The collaborative information system 222 illustrated in FIG. 2A includes a CIS platform 224 communicatively coupled to a plurality of collaborative information participants 238 interconnected via a communication network 239, each participant 238 having a data source 240. According to an example embodiment, the collaborative information system 222 can be implemented by a networked computing system such as the cloud computing system 100 illustrated in FIG. 1, with the CIS platform 224 being implemented as a cloud platform. That is, the CIS platform can be implemented using geographically diverse and dynamically-configured computing resources.

The CIS platform 224 is communicatively coupled to the data sources 240 associated with participants in the collaborative information system via communication link 239. The CIS platform 224 is programmed with CISs 226 (e.g., query services). Each query service 226 is implemented using one or more queries (e.g., 227-1, 227-2, . . . 227-N) operable on authorized portions of participant data sources 240. That is, each CIS can be a set of one or more queries involving the available data sources 240. A group of queries may be the same or different (e.g., more or less inclusive) than a query set, which is discussed further below. In other words, each query service may be implemented using a standardized group (e.g., “canned set”) of queries. The CIS platform 224 is further programmed with indications from individual ones of the plurality of collaborative information participants 238 authorizing some portion of their data source 240 to be available to the one or more queries (e.g., 227-1, 227-2, . . . 227-N) defined by at least one query service 226. Participants 238 can make all or part of their data source available to all or part of a respective query, or query set. A participant 238 may require its IT staff to enable a query or query set. However, once enabled, the participant may then authorize additional query services that already have their required queries implemented without further involvement of the IT staff.

FIG. 2B is a diagram illustrating another example computing platform for providing collaborative information services according to an example of the present disclosure. In addition to the query services 226, the CIS platform 224 can be programmed with a service modeling service 228, an authorization configuration service 230, an authorization and attestation service 232, a cloud index service 234, and an authentication service 236.

The service modeling service 228 describes the queries issued by each query service 226, as well as the attributes (e.g., format, scope) of the output results by a respective query service 226. The authorization configuration service 230 is a portal that allows CIS participants to control the access to their data sources by query services 226 and/or individual queries. The authorization portion of the authorization and attestation service 232 ensures that just authorized queries by authorized query services 226 access participant data sources 240. The attestation portion of the authorization and attestation service 232 logs interactions of the various services and the participant's data sources 240, if desired by a participant 238, to serve as an audit trail. The cloud index service 234 maintains a cache of authorized information from data sources 240 that enable the efficient implementation of query services which require information for just a fraction of the potentially large number of data sources 240.

The CIS platform 224 is programmed (e.g., with executable instructions stored in a memory and executable on a processor) to implement the following functionality. Participants 238 in the collaborative information system 222 authenticate with the CIS platform 224 (e.g., peer-to-platform and platform-to-peer, together referred to as peer-to-platform-to-peer) rather than directly with each other (e.g., peer-to-peer). For example, a first participant 238 can authorize the CIS platform 224 to execute certain query services and/or queries on certain portions of the first participant's data sources 240, providing the query results in certain, specified ways (explained further below). The first participant 238 can further authorize the CIS platform 224 to permit certain other participants to invoke the authorized query services (and/or queries) on the authorized portions of the first participant's data sources 240.

Thereafter, another participant 238, if authorized by the platform as a result of the platform being authorized to permit the another participant 238, can cause the CIS platform 224 to invoke an authorized query service 226 (and/or queries). That is, the first participant can authorize a query, a query set, and/or a CIS, to involve portions of the first participant's data sources specified by the first participant corresponding to each query. Subsequently, one or more participant(s), if authorized with respect to the query, or query set and/or a query service, can then execute the query, a query set, and/or a query service, to involve portions of the first participant's data sources that the first participant specified corresponding to a respective query. In this manner, the first participant does not have to individually authorize (and monitor or control) each subsequent participant individually that wishes to execute the query, or query set and/or query service. Provisions are explained below for creating new queries and/or query services (i.e., groups of queries).

The peer-to-platform and platform-to-peer authorization functionality of the CIS platform 224 enables participants 238 to authorize CIS services that access data in standardized (e.g., known) ways instead of having to manage point-to-point data sharing rules among participants that can be typical of previous information sharing approaches. The peer-to-platform and platform-to-peer authorization relationship structure, effectively a hub-and-spokes configuration, enables greater scalability from the perspective of managing the collaborative information system arrangements. The peer-to-platform and platform-to-peer authorization relationship structure, and standardized querying with known query service result attributes, also enables greater data sharing while greatly reducing the risk of data mining by competitors.

FIG. 3 is a diagram illustrating components of the collaborative information services platform according to an example of the present disclosure. A portal access system 342 includes a portal 344 communicatively coupled to a number of models and services. The portal 344 provides access to collaborative information system models that enable greater self-configuration by participants of the CIS platform (e.g., FIG. 2A at 224). Models refer to logic that may be implemented in hardware or by executable instructions stored in a memory and executable by a processor to perform a function. Participants configure models via the portal 344.

FIG. 3 shows portal 344 providing access to the service modeling service 328 via communication link 347. The service modeling service is communicatively coupled to a service model 346. An authorized service developer can use the portal 344 to manage the lifecycle of a particular service (e.g., a query service that relies on a set of one or more queries). The portal can support both human and programmatic interactions with the same level of functionality that includes the registration, categorization, and description of the service. The description of the service includes a description of the information used by the service (e.g., the queries), and the output provided by the service (e.g., the result attributes).

FIG. 3 shows portal 344 providing access to the service taxonomy model 348 via communication link 349. Participants can use the portal 344 to indicate which services in the service taxonomy model 348 they are willing to support for specific categories of data, and/or for particular locations of their data sources. The service taxonomy model 348 is communicatively coupled to the service modeling service 328 via communication link 363 such that they may exchange information. Services can be categorized to facilitate working with large numbers of services. For example, a participant may authorize a category of services instead of having to authorize a quantity of services individually. In addition, services properly added to a prior-authorized category may be authorized by virtue of the proper categorization to the authorized category.

Services can be categorized in hierarchies based on the service taxonomy model 348 that can reflect one or more of: type of service, type of result(s), and/or query/queries sets being executed to implement the service. Services can be related to other services, inherently or invoked by a participant in a related fashion (e.g., applying a logical function to the results of queries to arrive at a desired output). For example, a query service “A” may be implemented using queries that are a subset of a query service “B.” As such, query services “A” and “B” are inherently related, with query service “A” being a child of query service “B.” In another example, a participant may wish to interrogate data sources to find an output data set reflecting query service “C” AND query service “D.” In this manner, the participant invokes queries “C” and “D” in a related fashion. In yet another example a second query service may be run in the results of a first query service, such as a downstream consumer service may be run on a service to create an upstream set of data which data providers are willing to share with consumers.

The service taxonomy model 348 can be set up to be static rule based, and/or can include conditional taxonomies. For example, a data provider may be willing to share data for query service “C” run alone. The data provider may also be willing to share data for query service “D” run alone. However, the data provider may feel that the results of query service “C” AND query service “D” reveal too much information regarding the relationship of certain data in the data provider's data source. Therefore, the service taxonomy model 348 can reflect that the results of query service “C” AND query service “D” are not available at all, or that certain portions of the results are summarized to a higher level that is not so revealing, or obfuscated in some manner acceptable to the data provider. Taxonomies concerning related services can also be referred to as conditional taxonomies.

Queries themselves are described in the language(s) supported by data sources. Participants that are data source providers must enable support for such queries for a service to be able to run on their data source. Query sets are sets of queries that are often performed together, and can be authorized subject to use of an appropriate conditional taxonomy. A service (e.g., a query service, discovery service, or other service) can be implemented (e.g., use) using one or more queries, one or more query sets, or portions of one or more query sets. Several different services may have queries that belong to a particular query set. Where a participant authorizes a particular query set to involve portions of the participant's data sources, the participant may also authorize any service having queries derived entirely from the authorized particular query set. By authorizing a number of query sets, a participant can choose to authorize a wide range of services derived from the number of query sets implemented to operate on their data sources without having to evaluate (and authorize) the services individually. According to some examples of the present disclosure, a participant having a data source (e.g., data provider) can implement query sets with respect to their data source and use taxonomy model(s) to authorize services using queries of the implemented query sets. According to some examples, a participant may revoke or conditionally modify authorization of certain services despite having authorized a query set that includes each of the queries of the service. An authorization may be conditionally modified using a conditional taxonomy. For example, the relationships between individual services may be obfuscated for the presentation of data for an individual service. Therefore, a combination of two or more services (e.g., by logical operation) may not be possible without additional constraints even if the services are available individually. That is, a “composite” service may have different participation/access rights pursuant to a conditional taxonomy.

FIG. 3 shows portal 344 providing access to the query/query set model 356 via communication link 357. Participants must implement the queries and or query sets that are required for the services they choose to authorize. Implementations for query sets for particular data source products can be made available for download to participants via the Query/Query Set model 356. The query/query set model 356 is communicatively coupled to the service modeling service 328 via communication link 345, for example, to communicate to services authorization of particular queries and/or query sets.

FIG. 3 shows portal 344 providing access to the data source model 354 via communication link 355. Not all data sources will categorize data according to the data taxonomy model 350. The data source model 354 addresses this issue. If a participant's data source labels data according to the taxonomy of the data taxonomy model 350, then queries of a service are constrained based on the taxonomy of the data taxonomy model 350. Otherwise, the query and/or results are further processed to correspond the participant's data source labels to the taxonomy (e.g., according to a default mapping or list).

FIG. 3 shows portal 344 providing access to the participant taxonomy model 352 via communication link 353. The participant taxonomy model 352 defines groups of participants, such as end-consumers, growers, maintenance providers, etc. A participant may be part of zero or more groups as defined in the participant taxonomy model 352. Groups of participants can be used to further govern rights over who is permitted to invoke certain services that involve the participant's own data. That is, a participant may authorize a service to involve their data source except where the service is invoked by a specified other participant, group of participants, and/or or invoked along with (e.g., aggregated with) another service. For example, one service might provide product location information, and another service might provide product count information. A data provider may allow for other participants to run either service individually, but disallow running the two services in aggregate with one another since doing so exposes too much information (e.g., a product count at each location). Or a participant may authorize a service to involve some portion of their data source where the service is invoked by one participant/group, and may authorize a service to involve some other (more or less or different) portion of their data source where the service is invoked by another participant/group.

FIG. 3 shows portal 344 providing access to the data taxonomy model 350 via communication link 351. The data taxonomy model 350 can be configured by a participant to further define a scope of access to the participant's data source with respect to certain categories of the data, which may be further qualified by certain participants. That is, a participant may limit some (or all) portions of their data source for a particular service. For example, a participant may limit a service to involve data from their data source that is publically reported, rather than not authorize the service at all. Or a participant my limit the scope of their data source to certain relevant kinds of data for a service invoked by a specified participant, and/or subject to additional constraints with respect to combining (e.g., aggregating) services.

FIG. 3 shows portal 344 providing access to the authorization model 358 via the synthesizer choices 359 and communication links 360 and 361. A participant's configuration of one or more authorizations are synthesized into the authorization model 358, which is used to govern access to the participant's data sources. A participant's authorization configuration specification can also be captured directly into the authorization model 358. The authorization model 358 governs access to the participant's data sources by limiting the access of respective query services by authorized other participants to specified portions of the participant's data sources.

A participant-configured authorization model makes it easier for a participant (e.g., any size organization) to support their own participation in the collaborative information system than was experienced with previous (e.g., peer-to-peer) approaches where more intervention may be needed from IT staff. An example of a service that supports self-configuration for participants and the platform is the discovery service, which is discussed further with respect to FIG. 5. Like other services, the discovery service must be authorized by a participant. Once authorized for execution by the CIS platform, the discovery service peruses the service models of the participant's other authorized services, recognizes the kinds of product category and/or product IDs that are considered in the queries, and then interacts with a participant's data sources to discover which products the participant supports in its supply chain. This information is cached in a cloud index to support the efficient operation of other authorized services. It guides the other authorized query services to participant data sources that are relevant for the query service. Without such a discovery service, participants have to specifically register information they choose to authorize. Thus, self-configuration can benefit both the participant providing a data source, as well as the participant(s) that might wish to invoke services involving the data source that can function more efficiently due to the previous discovery process.

The service developer can describe a service, such as a query service, in the service model 346 using the service modeling service 328. The service developer can configure the service model 346 to indicate the queries and/or query sets that are used by a query service, for example. Participants can access the service model 346 via the portal 344 to learn the queries and/or query sets that are used by a particular query service.

FIG. 4 is a diagram illustrating an authorization and attestation service for a computing platform according to an example of the present disclosure. Authorization logic 464 includes authorization and attestation service 466 having inputs from an authorization model 458 and query services 446, and providing outputs to data sources 472 and a participant report repository 474. The function of the authorization and attestation service 466 is to ensure that the CIS platform (e.g., services such as query services 446) perform authorized queries, for authorized participants, involving authorized data sources, and does not perform unauthorized queries, queries involving unauthorized portions of data sources for a respective query, and/or queries invoked by unauthorized entities (including unauthorized participants).

In addition, another function of the authorization and attestation service 466 is to maintain attestation logs 468 that can be used to audit interactions between participants and the platform and/or data sources. The authorization and attestation service can log queries and/or service invocations, among other activities that may be of interest, and can report results to participants and/or system administrators. According to one example embodiment, reports are stored in a participant report repository 474 via communication link 476.

The authorization and attestation service is guided by the authorization models 458 as may be self-managed by each participant, including service relationship rules expressed in a conditional taxonomy, as previously discussed. The authorization models 458 communicate with the authorization and attestation service 466 via a communication link 478. The authorization and attestation service 466 can include a query shim 470, a “shim” in the sense of being logic that fits between two other logic components so as to relate them (e.g., facilitate communication of useful information therebetween). The query shim 470 is programmed to ensure that just authorized queries are made upon data sources 472 (e.g., via communication link 480), and that just authorized results are returned to the invokers of services. Authorized results may not include raw data from the data sources, or intermediate results (e.g., results computed from the raw data) in response to invoking a service. Authorized results returned to a participant may format, organize, and/or summarize query raw data and/or intermediate results into higher-level authorized results that aggregate the raw data and/or intermediate results in order to maintain confidentiality of individual raw data, according to the service description. In this way, the raw data from a data source and computed intermediate results are not exposed to an invoker of a service unless they are included in the definition of results for a particular service. Thus, a data source provider is always aware of what data will be returned to an invoker of a service and can use the knowledge to direct its own authorization choices.

FIG. 5 is a diagram illustrating a discovery service for a computing platform according to an example of the present disclosure. Discovery logic 582 includes the discovery service 584 communicatively coupled to the authorization model 558 via communication link 583, and communicatively coupled to the authorization and attestation service 566 via communication link 588, and communicatively coupled to an index service 586 (e.g., a cloud index service) via communication link 587. The discovery service 584 inspects the authorization model 558 to find what services are authorized by a participant. The services authorized by a participant are determined from the authorization and attestation service 566.

The discovery service 584 also inspects the queries of services and builds information regarding the kinds of master and transactional data that may be accessed from a participant's data sources 572. According to some examples of the present disclosure, master data can concern groups of items (e.g., classifications), whereas transaction data can concern individual items. For example with respect to a collaborative information service applied in regards to a supply chain, master data might concern attributes corresponding to various kinds of stereo equipment, but the discovery service might also discover transactional data such as the actual instances of stereo equipment in the data sources and activities (e.g., sale, fabrication steps, locations, data of manufacture, component types/sources, etc.) involving the actual instances of stereo equipment.

The discovery service 584 can then run queries to the participant's data sources 572, if authorized by respective participants, to find out what kinds of corresponding master and transactional data are actually present. The information that results from the discovery service 584 is cached in a collaborative information system index (e.g., a cloud index) 586, which can be subsequently used to support the more efficient (e.g., optimized) execution of query services. For example with respect to a collaborative information service applied in regards to a supply chain, a query service is invoked by a participant to operate on a particular brand of stereo components across a number of data sources. However, since the services are defined before they are invoked by a participant, the discovery service 584 may have previously run the queries comprising the service being invoked and cached the results in the cloud index 586. Then, in response to the service being invoked by a participant causing the queries, the cache can be used to quickly find which supply chain participants have such components, rather than having to query a large quantity of possible data sources in real time.

While a single cloud index is indicated in FIG. 5 for clarity, examples of the present disclosure are not so limited. That is, the collaborative information system of the present disclosure can include more than one cloud index, and/or cloud index caching arrangement (e.g., a cloud index and associated interfaces and supporting data processing hardware and/or programmed functionality, as is further discussed with respect to FIG. 6 below).

FIG. 6 is a diagram illustrating a cloud index cache arrangement according to an example of the present disclosure. The cloud index cache arrangement 690 includes a cloud index 692 communicatively coupled to each of a registration interface 694, a data discovery interface 696, a maintenance interface 698, and a query engine 699. The cloud index cache arrangement 690 supports the collaborative information services. As discussed above, the data discovery service (e.g., FIG. 5 at 584) populates the cloud index 692 with discovered information that can be used to optimize the execution of query services, for example, via a data discovery interface 696. The registration interface 694 and maintenance interface 698 may be standardized interfaces for configuring and managing the cloud index 692 respectively. The query engine 699 can be used to execute queries to populate and/or update the cloud index as may be directed by the data discovery service (e.g., FIG. 5 at 584).

A query shim (e.g., FIG. 4 at 470) can also interact with the cloud index 692 to obtain a list of data sources that may have data of interest to a query. The query shim ensures that only those data sources that have authorized the queries for the particular instance of a query service are able to provide data for the query service. Similarly, the query shim may interact with a number of cloud indexes as supported by different instances of the collaborative information services platform.

FIG. 7 is a diagram illustrating a serialized data service according to an example of the present disclosure. Data sources can include many types and classifications of data. One such data classification is master data and transactional (e.g., serialized) data. For example, participants in a collaborative information system applied with respect to a supply chain can have master data that describes attributes of the items which are the subject matter of the supply chain. Master data can be higher level information, describing groups. More specifically with respect to a supply chain example, master data may describe classes of products, types of products, product attributes, locations of interest with respect to the supply chain, and other information of the type that may be applicable to more than one supply chain item or activity. The volume of master data typically does not change with supply chain activity. However, there can be limited exceptions to the general condition that the volume of master data does not change with supply chain activity. If a new product type is designed or manufactured for the first time, new master data may be generated corresponding to the new product. However, the master data corresponding to the new product can remain static as additional quantities of the new product are manufactured. Master data may on rare instances need to be modified for an existing product. One example is if a product has been so successful that serialized product information is no longer derivable from the master. Another example is if product has been recalled such that only a portion of the master data is now relevant.

In contrast, the volume of transactional data typically does change (e.g., increase) with supply chain activity. For example, as a particular product is manufactured, data may be captured to record attributes specific to that particular product, such as date/time of manufacture, serial number, lot number, component inputs used in the product, present location, inventory quantity, etc. Transactional information can be generated over time. As such, new transactional information can be received to a data source over time in a serialized ordering. As such, time-based transactional data can also be referred to as serialized data. Serialized data captures information about events that happen as a supply chain operates. For example, the shipment of a product from one location to another is an event that occurs relative to a point in time and can have some corresponding serialized data. The volume of serialized data typically grows with supply chain activity. Again, there may be exceptions to the general condition that the volume of transactional data changes (e.g., increases) with supply chain activity, for example, where existing data is changed to reflect changes occurring in the supply chain, rather than creating new data, may not increase the volume of data. Transactional data may not be updated when the master data is updated. For example, in the case of recall within a supply chain, master data concerning a class of objects may need to change while the transactional data concerning each particular object remains the same.

Some collaborative information system participants may wish to have their serialized data hosted by a service. The advantages of such a serialized data hosting arrangement for the participants include not having to manage the increasing volumes of data, not having to maintain a highly available data source to provide information to the collaborative information system, and not having to manage one or more data retention policies that may be applicable to the serialized data. As used herein, a data retention policy refers to rules, other than those related to a measure of quality of a particular data item (e.g., checksum, parity, etc.) by which a determination can be made to retain (or not) data within a non-transitory medium. For example, data that is not stored in a storage medium due to a data quality and/or data integrity problem is not typically an application of a data retention policy. However, data that is stored for a certain period of time and then removed (e.g., can no longer be accessed or retrieved such as by the change of an index to the data even where a memory actually remains programmed with a data item) according to a predefined date-related criteria can be an application of a data retention policy. According to some examples, the data source of the host serialized data service may contain data on behalf of multiple collaborative information system participants.

FIG. 7 illustrates one example implementation of a serialized data service arrangement 781. A serialized data service 783 can receive data from a data source 772 via communication link 775. The data source 772 may be that of a collaborative information system participant, which may be an entity that is part of a supply chain, and the serialized data service 783 may be that of a host entity. The data source 772 may or may not be a persistent store of data, or may be of sufficient volume to store serialized data for some finite period of time.

Data can then be communicated to a serialized-data data source 789 via communication link 797, and stored therein. The serialized-data data source 789 may be used as a data source for a collaborative information system on behalf of the participant. That is, the serialized-data data source 789 may be communicatively coupled to the computing platform programmed with the collaborative information services as shown at 240 in FIGS. 2A and 2B, and similarly utilized. As with other data sources, such as those directly provided by a participant and as described above, access to data within the serialized-data data source 789 by other participants in the collaborative information system is governed by the participant's authorization model (e.g., FIG. 3 at 358).

The serialized data in the serialized-data data source 789 may be subject to and governed by one or more retention policies. Retention policies may be implemented by retention policy data taxonomy model 791. A retention policy data taxonomy model 791 is communicatively coupled to the serialized-data data source 789 by communication link 793, such that the retention policy logic 791 may operate on the data stored in the serialized-data data source 789. For example, retention policy data taxonomy model 791 may specify to delete a certain portion of data stored in the serialized-data data source 789 after a particular date reflective of a data retention policy applicable to the certain portion of data.

The retention policy data taxonomy model 791 may be configured by the participant whose data is stored in the serialized-data data source 789 (e.g., the data provider), for example, to implement applicable retention policies. Alternatively and/or in addition, the retention policy data taxonomy model 791 may be configured by a third party on behalf of the participant whose data is stored in the serialized-data data source 789, such as by the host of the serialized data service 783, to implement applicable retention policies.

According to some example implementations of the serialized data service arrangement 781, the serialized data service 783 may pull data from a participant's data source(s) 772, for example via communication link 775. The serialized data service 783 can operate as other services supported by the collaborative information system computing platform, and can therefore be governed by a participant's authorization model (e.g., FIG. 3 at 358).

According to some example implementations of the serialized data service arrangement 781, if a participant wants to push data from the participant's data source(s) 772 to the serialized data service 783, the data can first be pushed to a proxy data storage medium 785 via a communication link 771. The proxy data storage medium 785 receives and temporarily caches the pushed data until it is pulled by the serialized data service 783 via communication link 773.

A participant, and/or an authorized third party (e.g., a host) can set one or more retention policies for applicable portions of serialized data by configuring the retention policy data taxonomy model 791. The one or more retention policies can be enforced by the serialized data service 783 (e.g., as communicated over communication link 795) and/or the serialized-data data source 789 (e.g., as communicated over communication link 793).

According to a more specific example of implementing a retention policy, the serialized data service 783 can augment a particular serialized data item with one or more appropriate tags that reflect the one or more retention policies that govern(s) the particular data item (e.g., item of data stored in a data source such as a database). The relation between a data item and one or more retention policies can be defined in a retention policy data taxonomy model 791 that is managed as part of the serialized data service 783, for example. A data provider 738 (i.e., a participant having a data source) can configure a data source via communication link 762, and can configure the retention policy data taxonomy model 791 via communication link 765. The data item tagging process may be subject matter (e.g., supply chain), time/date, and/or location specific as specified in the retention policy data taxonomy model 791.

Some retention policies may dictate that affected data be retained for a specified period of time (e.g., two years), and then deleted thereafter. Other retention policies may be associated with specific subject matter (e.g., a particular supply chain) and further based on location (e.g., a location where the data was captured and/or the location where a product was finally sold. Other retention policies may be based on one or more regulatory requirements, which can be complex (e.g., for a globally distributed supply chain) associated with location of database items, border-crossing activities, and/or item ownership nationality, among other considerations. Some retention policies can also be logical combinations of other retention polices, or be made to include conditional criteria.

Conflicts in a retention policy applicable to a particular data item (e.g., of a data source) that can be recognized at the time of policy configuration can be brought to the attention of the data provider 738 (e.g., via communication link 765). Recommendations for resolving the conflict may be given (e.g., a suggested ordering for the policy rules to be implemented such as superseding rights for a given policy in comparison to another). Conflicts that are recognized at the time of policy implementation can similarly be brought to the attention of the data provider, possibly with recommendations for resolving the conflict. One solution for resolving retention policy conflicts is for the data provider to specify a final ordering for the implementation of the conflicting retention policy rules.

Retention policy rule conflicts can be resolved in other ways too. Retention policies can be mapped onto a same generalized graph or tree, and the policy recommendations at each tree compared in order to detect conflicts. Several retention policy conflict resolution methodologies are possible, including: (1) one retention policy overrides another (e.g., always); (2) a superset retention policy invoking conflicting retention policies in a most restrictive combination is provided; (3) neither conflicting retention policy applies and the applied retention policy defaults to a “safe” retention policy where the retention policy conflict cannot be resolved; and/or (4) full restriction until a manual fix provided. The above-mention retention policy conflict approaches are non-exhaustive, and other possible actions are contemplated within the scope of the present disclosure.

The collaborative information services computing platform can be programmed to track and implement such requirements on behalf of its many participants (e.g., with respect to a supply chain, industry, etc.) rather than each participant having to independently do so for each data source or group of data sources. Thus, the capability for centralized implementation of retention policies and/or uniform application across numerous data sources can help to increase the ability of organizations of all sizes to participate in collaborative information systems by reducing the associated burden of managing data in data sources.

The serialized data service 783 can make it easier for collaborative information system participants to have their data hosted, to have their data contribute to the results collaborative information services, and to ensure that their data adheres to appropriate retention policies. Many data providers, that are collaborative information system participants, especially those from smaller organizations, may benefit greatly from outsourcing the hosting of their serialized data. This frees a participant from the costs (including time) of hosting and managing a highly available data source.

A data provider that has its data reliably available to a collaborative information system may be able to participate in strategies together with other participants that reduce costs and/or energy usage, among others. Participants can take advantage of the availability of data retention policies as supported by the collaborative information system. Participants can benefit from others having implemented a required policy rather than having to individually implement it. Certain retention policies can be configured to adhere to regulations as required by local laws simplifying participation in global trade.

The serialized data service arrangement 781 illustrated in FIG. 7 is compatible with the collaborative information services computing platform (e.g., FIG. 2B at 224). That is, the serialized-data data source 789 can be utilized similar to data source 240 illustrated in FIG. 2B. The serialized data service 783 can be configured and managed in a manner described for other services with which the computing platform is programmed. For example, serialized data service 783 can be managed such that only authorized data is stored therein, according to the same authorization model (FIG. 3 at 358). As described previously for data sources in general, the authorization model can also be configured to define how serialized data service 783 data may be used by other collaborative information services.

FIG. 8 is a flow chart illustrating an example of a method for serialized data service 801 according to an example of the present disclosure. The method 801 includes retrieving serialized data to a serialized data service 803. The method further includes augmenting the serialized data with information corresponding to one or more data retention policies 809. The augmented serialized data is stored to a data source 811. The method also includes removing the augmented serialized data from the data source based on the augmented information 813.

Machine readable and executable instructions and/or logic, which are operable to perform the method described in connection with FIG. 8, can be present in whole or in part in the examples of other figures. Embodiments, however, are not limited to the particular examples given herein.

Applying a common authorization model to data sources, including the serialized data service 783 and/or serialized-data data source 789 reduces the likelihood of inconsistencies when managing authorizations. Prior approaches do not appear to exploit a single multi-dimensional authorization model to guide the storage of data in a data source, control data access to data provider authorized activities, or support implementation of subject matter aware (e.g., associated with a supply chain) and/or location aware retention policies for data that is available to the collaborative information system. Similar operability of data sources and services across the collaborative information system can reduce the challenges for a participant associated with participating in the collaborative information system.

The above specification, examples and data provide a description of the method and applications, and use of the system and method of the present disclosure. Since many examples can be made without departing from the spirit and scope of the system and method of the present disclosure, this specification merely sets forth some of the many possible embodiment configurations and implementations.

Although specific examples have been illustrated and described herein, those of ordinary skill in the art will appreciate that an arrangement calculated to achieve the same results can be substituted for the specific examples shown. This disclosure is intended to cover adaptations or variations of one or more examples of the present disclosure. It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combination of the above examples, and other examples not specifically described herein will be apparent to those of skill in the art upon reviewing the above description. The scope of the one or more examples of the present disclosure includes other applications in which the above structures and methods are used. Therefore, the scope of one or more examples of the present disclosure should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.

Various examples of the system and method for collaborative information services have been described in detail with reference to the drawings, where like reference numerals represent like parts and assemblies throughout the several views. Reference to various examples does not limit the scope of the system and method for displaying advertisements, which is limited just by the scope of the claims attached hereto. Additionally, any examples set forth in this specification are not intended to be limiting and merely set forth some of the many possible examples for the claimed system and method for collaborative information services.

Throughout the specification and claims, the meanings identified below do not necessarily limit the terms, but merely provide illustrative examples for the terms. The meaning of “a,” “an,” and “the” includes plural reference, and the meaning of “in” includes “in” and “on.” The phrase “in an embodiment,” as used herein does not necessarily refer to the same embodiment, although it may.

In the foregoing Detailed Description, some features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the disclosed examples of the present disclosure have to use more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 

What is claimed:
 1. A method for a serialized data service, comprising: retrieving, via a server comprising one or more processors, serialized data to a data service; augmenting the serialized data with information corresponding to one or more data retention policies; storing the augmented serialized data to a data source; removing the augmented serialized data from the data source based on the augmented information; configuring an authorization model to specify attributes of authorized services involving the data source, wherein the authorization model specifies attributes of authorized services involving the data source, including query services and the data service; configuring a retention policy to specify a correspondence between the one or more data retention policies and the augmented information; and configuring a retention policy data taxonomy model to specify a correspondence between the one or more data retention policies and the augmented information.
 2. The method of claim 1, wherein retrieving serialized data to the serialized data service includes retrieving the serialized data from a data source of a data provider.
 3. The method of claim 1, further comprising pushing the serialized data from a data source of a data provider to a proxy data storage medium, wherein retrieving serialized data to the data service includes retrieving the serialized data from the proxy data storage medium.
 4. The method of claim 1, wherein the data source is available to a query service invoked by a participant in a collaborative information system.
 5. The method of claim 4, further comprising invoking the data service through the collaborative information system, wherein retrieving serialized data includes obtaining the serialized data as results of a query of the data service.
 6. The method of claim 1, wherein the query service includes a set of queries that are performed together and authorized by the authorization model.
 7. The method of claim 1, further comprising modifying, conditionally, authorization of certain services despite having authorized a query set within the query service that includes each of the queries for the service.
 8. The method of claim 1, wherein the one or more data retention policies are based on an age of the serialized data.
 9. The method of claim 1, wherein the one or more data retention policies are based on a location of where the serialized data was captured.
 10. The method of claim 1, wherein the resolution recommendation includes an action selected from the group comprising: always overriding a particular one of the one or more data retention policies in favor of another one of the one or more data retention policies; providing a superset data retention policy invoking a most restrictive combination of the one or more data retention policies; providing a default safe data retention policy in lieu of the one or more data retention policies; and fully restricting the serialized data until a manual fix can be provided.
 11. The method of claim 1, wherein: the one or more data retention policies include a set of rules that are applied to retain the serialized data within a non-transitory medium; and the set of rules specify a deletion of a certain portion of data stored in a serialized-data data source at a particular date.
 12. A non-transitory computer-readable storage medium having computer-readable instructions stored thereon that, if executed by one or more processors, cause the one or more processors to: retrieve serialized data to a serialized data service; augment the serialized data with information corresponding to one or more data retention policies to which the serialized data is subject; enforce the one or more data retention policies upon the serialized data based on the augmented information and specify a correspondence between the one or more data retention policies; configure a retention policy data taxonomy model to specify a correspondence between the one or more data retention policies and the augmented information; and configure an authorization model to specify attributes of authorized services involving the data source, wherein the authorization model specifies attributes of authorized services involving the data source, including query services and the data service.
 13. The non-transitory computer-readable medium of claim 12, wherein the computer-readable instructions to retrieve serialized data to a serialized data service includes computer-readable instructions to retrieve the serialized data from a data source of a data provider.
 14. The non-transitory computer-readable medium of claim 12, wherein the computer-readable instructions to retrieve serialized data to a serialized data service includes computer-readable instructions to retrieve the serialized data from the proxy data storage medium.
 15. The non-transitory computer-readable medium of claim 12, wherein the computer-readable instructions to configure the authorization module includes computer-readable instructions to conditionally modify authorization of certain services among the query services.
 16. A computing system, comprising: a plurality of collaborative information participants interconnected via a communication network, each participant having zero or more data sources; a computing platform programmed with a number of services including a query service and a serialized data service, the query service using one or more queries operable on authorized portions of participant data sources; wherein the serialized data service is operable to: retrieve serialized data from a data source of at least one participant; configure an authorization model to specify attributes of authorized services involving the data source, wherein the authorization model specifies attributes of authorized services involving the data source, including query services and the data service; augment the serialized data with information corresponding to one or more data retention policies; enforce the one or more data retention policies upon the serialized data based on the augmented information; and configure a retention policy data taxonomy model to specify a correspondence between the one or more data retention policies and the augmented information.
 17. The system of claim 16, wherein the data source is available to a query service invoked by a participant in a collaborative information system.
 18. The system of claim 16, wherein the query services includes a set of queries that are performed together and authorized by the authorization model subject to a conditional taxonomy.
 19. The system of claim 16, wherein the serialized data service is operable to remove the augmented serialized data from the data source based on the augmented information. 